fix: readme - #21
Conversation
|
Warning Review limit reached
Next review available in: 38 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Comment |
Greptile SummaryThe README now replaces the hidden 1×1 visitor counter with a centered, labeled Visitors badge. Browser rendering confirmed that the badge is visible, centered, exposes the alternative text “Visitor count,” and loads successfully from the Komarev image endpoint. No defects were found. Confidence Score: 5/5Safe to merge: the visible visitor badge renders and loads as intended. The changed Markdown and HTML path was exercised in a browser against both the previous and current README, including layout, image visibility, accessible text, and the external image response. Files Needing Attention: No files need further attention.
 T-Rex LogsWhat T-Rex did
Reviews (1): Last reviewed commit: "fix: readme" | Re-trigger Greptile |
1 participant
Make visitor counter badge visible (centered, for-the-badge style).